Blog

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

I have had some suggestions for the fwreinit flag to be protected in order to reinitialize the application at hand. What do you think? Is this overkill? The application reinitializes, but it does not crash. It just adds some extra cycles to the request in order to clear and reinit the app. Please send me your comments, suggestions? Should an application reinit, be password protected? Thanks, Luis

Add Your Comment

(3)

Dec 06, 2006 03:53:29 UTC

by Sana

Hi Luis, I think it really important to keep our APP more secure. Why we allow site users to reinit our app. some users they just play with these kind of things and keep reinit app. In my app i am using onAppinit method to call global components + static data queriries and other global static info. so keep reinit the app cause some problem of server timeout and also whole system get very slow. Thanks Sana

Dec 06, 2006 08:38:38 UTC

by Rob Gonda

If you allow to set a init key and init password is enough. You can set it to a complex password which no user could guess. That's secure enough for me. p.s. this captcha text is really annoying. Check out Charlie's solution, also default in a latest version of blogCFC

Dec 06, 2006 15:26:06 UTC

by Luis Majano

Thanks Rob!! You are the details man!! jeje. Will take a look at it.

Recent Entries

12 Days of BoxLang - Day 4: TestBox

12 Days of BoxLang - Day 4: TestBox

Today we’re celebrating one of the most exciting new additions to the BoxLang ecosystem:

the TestBox BoxLang CLI Runner — a fast, native way to run your TestBox tests directly through the BoxLang Runtime. ⚡

No server required. No CommandBox needed. Just pure, ultra-fast BoxLang-powered testing from the command lineon Windows, Mac, and Linux.

If you’re building modern applications with BoxLang — web apps, CLIs, serverless functions, Android apps, or OS-level utilities — this new feature gives you a unified, flexible testing workflow you can run anywhere.

Victor Campos
Victor Campos
December 13, 2025
12 days of BoxLang - Day 3: SocketBox!

12 days of BoxLang - Day 3: SocketBox!

As BoxLang continues evolving into a modern, high-performance, JVM-based runtime, real-time communication becomes essential for the applications we all want to build: dashboards, collaboration tools, notifications, live feeds, multiplayer features, and more.

That’s where SocketBox steps in — the WebSocket upgrade listener built to work seamlessly with CommandBox and the BoxLang MiniServer. ⚡

Today, for Day 3, we’re highlighting how SocketBox supercharges BoxLang development by giving you fast, flexible, and framework-agnostic WebSocket capabilities.

Maria Jose Herrera
Maria Jose Herrera
December 12, 2025
12 Days of BoxLang - Day 2: CommandBox

12 Days of BoxLang - Day 2: CommandBox

BoxLang + CommandBox: The Enterprise Engine Behind Your Deployments

For Day 2 of our 12 Days of Christmas series, we’re diving into one of the most powerful parts of the BoxLang ecosystem: CommandBox the defacto enterprise servlet deployment platform for BoxLang.

If BoxLang is the language powering your applications, CommandBox is the engine room behind it all. ⚙️

Victor Campos
Victor Campos
December 11, 2025